traceability column in abaselined set module

SystemAdmin - Fri Sep 14 09:28:43 EDT 2012

You're going to need to learn about how to get a handle to the specific version of the source\target module at the other end of a link that is included in the Baseline Set. I would recommend that you have a look at "Modules->Baselines" section of the DXL Reference manual which you will find under the Help menu of the DOORS Explorer or Help menu of a Formal Module.

Alternatively, run the Analysis Wizard to create a simple DXL Layout trace column in a module, then inspect the DXL code that the Analysis Wizard creates. The Analysis Wizard uses handles for module versions and will give you an idea of how it should be done. For example, here's some snippets of code from the Analysis Wizard for tracing incoming links
 

ModuleVersion otherVersion = null
.
.
. 
for l in all(o<-linkModName) do {
     otherVersion = sourceVersion l
     otherMod = module(otherVersion)
     if (null otherMod || isDeleted otherMod) continue
     othero = source l
     if (null othero) {
            load(otherVersion,false)
     }
.
.
.

Paul Miller,
Melbourne, Australia

jlnddn - Mon Sep 17 07:19:49 EDT 2012
OK thank you.
It will be very difficult for me to make a generic script because in my project, I have several modules linked to another one like this :
A <- B
A <- C ...
If the major or minor of baseline for the modules B or C... are different how do I do? Especially if the baseline contained in the baseline set is not the last baseline ! Because I cannot use the getMostRecentBaseline...

SystemAdmin - Mon Sep 17 18:21:12 EDT 2012
If A, B and C were all included as members of a Baseline Set, then the Baseline Set will capture the link data between the specific individual baseline versions of modules A, B and C.

When you open and view each of the individual baseline versions of modules A, B and C that are members of the Baseline Set, the links between A, B and C will only go between the versions of the modules that are associated with that Baseline Set.

The generic code that I showed above will only show the links between the versions of Modules A, B and C that are members of the Baseline Set.

For example. Assume that the following represents the current individual baseline versions of modules A, B and C.
A(2.3) <-- B(3.0)
A(2.3) <-- C(1.2)
A new Baseline set is now created and we give it the name "XYZ". Modules A, B and C are defined to be members of the Baseline Set "XYZ".

Baseline Set "XYZ" is now configured to create its first Major Baseline Set - "XYZ(1.0)"

The Major Baseline Set "XYZ(1.0)" is now closed. This will cause the individual baseline versions of modules A, B and C to be pushed up to the their next Major versions. The following baseline versions of Modules A, B and C and the links between these versions are now locked into and associated with Baseline Set "XYZ(1.0)"
A(3.0) <-- B(4.0)
A(3.0) <-- C(2.0)
When you open and view Module A(3.0), DOORS will know that this version is a member of Baseline Set "XYZ(1.0)" and that Modules B and C also have specific versions that are members of the same Baseline Set. So the links from Module B to Module A will only be from version 4.0 of Module B, and the links from Module C will only be from version 2.0 of Module C.